Identity verification systems and methods

ABSTRACT

Systems and methods are disclosed for verifying customer identifications. In one embodiment, the method comprises receiving, at a transaction gateway, a communication associated with a transaction initiated by a customer; determining the communication includes an identity verification request to verify encoded data obtained from an identification presented by the customer; routing the identity verification request to an identity verification service; receiving, from the identity verification service, a result including one or more identification values obtained from the encoded data; and transmitting the result to a requester associated with the communication.

BACKGROUND OF THE INVENTION

Customers of various businesses, such as retail merchants, governmententities or financial institutions, are often required to present anidentification to complete a transaction. For instance, a merchant mayrequire customer identification for various types of purchases (e.g.,alcohol, lottery or tobacco purchases) or when certain types of payments(e.g., checks, credit cards) are presented to pay for transactions.Financial institutions usually require customers to present anidentification to complete a withdrawal or deposit transaction, cash acheck, or open a new account. Government entities may requireidentification for access into secure areas or other purposes. Otherbusinesses may also require identification from customers.

Unfortunately, a number of advances have been made in counterfeitingtechnology which make it increasingly difficult for the naked eye todistinguish legally issued identification documents from fraudulentidentification documents. In response, government agencies and otherentities are issuing identification documents/cards in which data isencoded within a magnetic stripe and/or two-dimensional barcode. Inorder to validate and verify the encoded information contained withinthe magnetic stripe or two-dimensional barcode, a business needs topurchase a hardware device (e.g., an IDLogix C100 Terminal) that willread and validate the encoded data. Thus, businesses must attach yetanother hardware device to their existing transaction systems.Additionally, identity verification may add one more processing stepthat must be completed in a transaction with a customer.

BRIEF SUMMARY OF THE INVENTION

Methods, systems, and machine-readable mediums are disclosed forverifying customer identifications. In one embodiment, the methodcomprises receiving a communication at a transaction gateway. Thecommunication is associated with a transaction initiated by a customerand includes one or more requests. Each of the requests are associatedwith a transaction service. The transaction gateway determines whetherthe communication includes an identity verification request to verifyencoded data obtained from an identification presented by the customer.The identity verification request is routed to an identity verificationservice. A result from the identity verification service is received atthe transaction gateway. The result includes one or more identificationvalues obtained from the encoded data. In some aspects, the result mayalso include a status indicating an outcome of the identityverification. By way of example, the status may indicate theidentification is expired, a format associated with the encoded data isinvalid, or the identification may be falsified. The result istransmitted to a requester (e.g., point-of-sale device, financialinstitution computer) associated with the communication. In someembodiments in which the communication includes a plurality of requests,transmitting the result may comprise transmitting a result messagehaving a plurality of results, each result associated with one of therequests.

In further embodiments, the method may comprise parsing, at the identityverification service, the encoded data to obtain the one or moreidentification values. The identification values may vary depending uponthe type of identification presented. For instance, the identificationpresented may be a driver's license, a state issued identification, apassport, or a military identification. Exemplary identification valuesobtained may include name, birth data, address, gender, hair color,height, eye color, and/or weight. Other identification values may alsobe obtained. The identity verification service may also determine acriteria is satisfied indicating the identification may be fraudulent(e.g., the identification has been presented a predetermined number oftimes within a predetermined time period). The result transmitted by theidentity verification service may include information that indicates theidentification may be fraudulent. Other status information may also betransmitted by the identity verification service.

Additional requests included in the communication may also betransmitted to other transaction services. For example, the method mayadditionally comprise determining the communication includes an identityvalidation request to assess validity of the identification. Theidentity validation request may be routed to an identity validationservice and a validation result may be received indicating anidentification validity status assessed by the identity validationservice. In one aspect, the identity validation service may assess thevalidity by comparing at least one of the identification values to adatabase including suspicious data values. If the identification valuematches a suspicious data value, the identity verification service maytransmit a validity status indicating a potential fraudulentidentification. In another aspect, the identity validation service mayassess the validity by matching one of the identification values to afirst stored value and retrieving a second stored value associated withthe first stored value. The second stored value and a second one of theidentification values both have a first attribute type. If the secondidentification value does not match the second stored database value,the identity verification service may transmit a validity statusindicating an alert.

Another example of a type of request that may be included in thecommunication is a check validation request. Thus, the method maycomprise determining that the communication includes a check validationrequest to analyze a loss potential associated with a check presentedfor payment for the transaction and routing the check validation requestto a check validation service.

In a second embodiment, a method is disclosed which comprises receivinga communication at a transaction gateway. The communication isassociated with a transaction initiated by a customer. A determinationis made that the communication includes a plurality of transactionservice requests and that one of the transaction service requests is anidentity verification request to verify encoded data obtained from anidentification presented by the customer. The first transaction servicerequest is transmitted to an identity verification service. A secondtransaction service request is also transmitted from the transactiongateway to a second transaction service. The transaction gatewayreceives a result from both the identity verification service and thesecond transaction service. The transaction gateway then transmits aresponse to a requester associated with the communication. The responseincludes the first result and the second result.

In a third embodiment, a system is disclosed which comprises acommunications interface, to receive a communication associated with atransaction initiated by a customer and to receive an identityverification result from an identity verification service and one ormore additional results. Logic is communicatively coupled with thecommunications interface. The logic is configured to determine thecommunication includes an identity verification request to verifyencoded data obtained from an identification presented by the customerand to transmit the identity verification request to the identityverification service. Logic also determines the communication includesone or more additional transaction service requests for the transactionand transmits each of the additional transaction service requests to atransaction service associated with the respective additionaltransaction service request. Logic also is configured to transmit aresponse to a requester associated with the communication. The responseincludes the identity verification result and the one or more additionalresults.

The system may also comprise the identity verification service to obtainone or more identification values from the encoded data and to transmitthe identity verification result to the communications interface. A datastore may be communicatively coupled with the identity verificationservice. The data store stores identity information for a plurality ofidentifications. The identity verification service may further beconfigured to compare the one or more identity values obtained from theencoded data to information in the data store to determine if theidentification may be fraudulent.

BRIEF DESCRIPTION OF THE DRAWINGS

Illustrative embodiments in accordance with the invention areillustrated in the drawings in which:

FIG. 1 illustrates an exemplary embodiment of a transaction system;

FIG. 2 is a block diagram of an exemplary identity verification servicethat may be used to verify identifications;

FIG. 3 is a block diagram of an exemplary computer system upon whichcomponents of the transaction system may be implemented;

FIG. 4 is a flow diagram illustrating an exemplary method that may beused to process a customer transaction; and

FIG. 5 is a flow diagram illustrating an exemplary identity verificationprocess.

DETAILED DESCRIPTION

In the following description, for the purposes of explanation, numerousspecific details are set forth in order to provide a thoroughunderstanding of the present invention. It will be apparent, however, toone skilled in the art that the present invention may be practicedwithout some of these specific details. In other instances, well-knownstructures and devices are shown in block diagram form.

FIG. 1 illustrates an exemplary embodiment of a transaction system 100.The transaction system 100 includes a transaction gateway 102communicatively coupled with point-of-sale device(s) 104, financialinstitution(s) 110, and client computer(s) 114. The transaction gateway102 is also communicatively coupled with a plurality of transactionservices, such as identity verification service 118, identity validationservice 120, check verification service 122, and other transactionservice(s) 124.

Point-of-sale device(s) 104 may be used to perform merchant and/orcustomer functions related to transactions initiated by customers, suchas a transaction for the purchase of goods or services or a moneytransfer transaction. For example, point-of-sale device(s) 104 may beused to receive payment (e.g., check, credit card, debit card, storedvalue card, or other payment type) for the transaction from thecustomer. As another example, point-of-sale device(s) 104 may be used byan agent to enter details of a money transfer transaction (e.g.,recipient information, money transfer amount) using point-of-saledevice. In some instances, the merchant may require the customer topresent an identification to complete the transaction. Theidentification may be used to verify the customer's identity. Thus,point-of-sale device(s) 104 may include a magnetic card reader, a twodimensional bar code reader, a smart chip reader, or other component toread encoded data on identifications presented by customers.Point-of-sale device(s) 104 may also include other components andperform other functions, such as one or more of the components orfunctionality described in U.S. application Ser. No. 10/116,689,entitled “Systems and Methods for Performing Transactions at APoint-of-Sale”, filed Apr. 3, 2002, the details of which are herebyincorporated by reference.

Financial institution system(s) 110 may be used to perform tellerfunctions, loan services, new account creations, or other types offunctions needed for customer transactions. A financial institution mayrequire the customer to present identification to verify the customer'sidentity in order to complete a transaction. Thus, financial institutionsystem(s) may be communicatively coupled with reader device(s) 112 toread encoded data on identifications. By way of example, readerdevice(s) 112 may be magnetic card readers, two-dimensional bar codereaders, smart chip readers, or other type of reader device used to readdata encoded on identifications.

Other types of client computer(s) 114 may also be communicativelycoupled with transaction gateway 102. For example, a client computer 114may be used to process patient transactions for a doctor or hospital. Asanother example, a client computer 114 may be used to processtransactions for a government agency. As with merchant and financialtransactions, entities interacting with customers may require customersto present identifications. Similar to reader device(s) 112, readerdevice(s) 116 may be communicatively coupled with client computer(s) 114and used to read encoded data on identifications presented by acustomer.

Transaction details may be submitted to a transaction gateway 102 bypoint-of-sale device(s) 104, financial institution system(s) 110, orclient computer(s) 114 in communications submitted to a transactiongateway 102. A communication may include one or more requests to performa transaction service to process the transaction and transactiondetails. Transaction gateway 102 may then be used to route requestsincluded in a communication to the appropriate transaction service. Insome embodiments, transaction gateway 102 may also include additionallogic to determine whether and when to process requests received in acommunication. Some transaction service requests may be routedsimultaneously to the appropriate transaction service 118, 120, 122,124. Other transaction service requests may be routed after results havebeen received from a previously routed transaction service request. Insome instances, transaction gateway 102 may not route some of therequests based on results from previous requests.

One example of a request that may be included in a communication totransaction gateway 102 is an identity verification request. An identityverification request may include encoded data associated with anidentification presented by a customer. By way of example, the encodeddata may have been read from a driver's license, a state issuedidentification, a passport, a military identification, a health card, orother type of identification presented by a customer. Transactiongateway 102 may route the identity verification request to an identityverification service 118. As will be described in further detail withreference to FIG. 5, identity verification service 118 may be used toobtain one or more identity values from the encoded data.

In some embodiments, identity verification service 118 may also be usedto transmit a status indicating an outcome of the identity verificationprocess. For example, the status may indicate whether the identificationis expired or whether the encoded data format is invalid. In someembodiments, status information may indicate whether the identificationmay be falsified. In those embodiments, identity verification servicemay be communicatively coupled with a data store (e.g., a relational orother type of database, text file, internal software lists, or othertype of data storage). The data store (not shown) may store informationused by the identity verification service to assess whether an identitymay be fraudulent. For example, the data store may store identificationswhich are known to be fraudulent. Other information may also be storedand used by identity verification service to verify identifications. Inother embodiments, identity verification service 118 may not becommunicatively coupled with a data store.

Another example of a request that may be included in a communication totransaction gateway is an identity validation request. Transactiongateway 102 may route an identity validation request to an identityvalidation service 120. Identity validation service 120 may then be usedto assess the validity of the identification. In some instances, thecommunication received at the transaction gateway, which included theidentity validation request, may include identity values associated withan identification presented by a customer. Alternatively, transactiongateway 102 may wait until identity values obtained from encoded dataare received from an identity verification service 118 and then transmitthe identity validation request and the identity values to identityvalidation service 120.

Identity validation service 120 may use the identification values todetermine whether the identification presented may be fraudulent or isotherwise problematic. A result indicating an outcome of the identityvalidation may then be transmitted by identity validation service 120 totransaction gateway 102. In some embodiments, the identity validationservice 120 may compare one or more of the identification values to adatabase including suspicious values. If there is a match, identityvalidation service 120 may transmit a response indicating an alertstatus. Alternatively or additionally, identity validation service 120may match one or more of the identification values to stored values in adata store. Stored values associated with the matched stored value maybe retrieved and compared to other identification values received by theidentity validation service 120. If one or more of the stored values donot match one or more of the received identity values, an alert statusmay be transmitted by the identity validation service 120. As anexample, identity validation service 120 may receive a social securitynumber as one of the identity values. The social security number may beused to retrieve stored values associated with the social securitynumber, such as a name. If one or more of the retrieved stored values(e.g., name, address, etc.) does not match the corresponding identityvalue received by the identity validation service 120, the identityvalidation service 120 may determine the identity may be fraudulent andmay transmit an alert status. Additional information about the identityvalidation may also be transmitted by identity validation service 120.It should be appreciated that other identity values associated withattributes other than social security number may alternatively oradditionally be used by identity validation service 120 to retrievestored information. Additional details of an account verificationdatabase and methods that may be used by an identity validation servicemay be found in U.S. application Ser. No. 10/773642, entitled“Account-Owner Verification Database”, filed Feb. 6, 2004, the detailsof which are hereby incorporated by reference.

A third example of a request that may be included in a communicationtransmitted to transaction gateway 102, is a request to validate a checkpresented by a customer as payment or partial payment for a transaction.Transaction gateway 102 may route the check validation request to checkvalidation service 122. Check verification service 122 may then analyzea loss potential associated with the check. A result of the checkvalidation may then be transmitted back to transaction gateway 102.Further details of an exemplary check validation system may be found inU.S. application Ser. No. 10/047917, entitled “System and Method forOverturning of Risk Eval Risk Model to Control Financial Risk”, filedJan. 14, 2002, the details of which are hereby incorporated byreference.

Other types of requests may also be included in a communication receivedat transaction gateway 102. Transaction gateway 102 may route theserequests to the appropriate transaction service 124. By way of example,the communication may include a money transfer request. Transactiongateway 102 may route the money transfer request to a money transfersystem. Further details of exemplary money transfer transactions andsystems are disclosed in U.S. application Ser. No. 09/975,171, entitled“Method and System for Performing Money Transfer Transactions, filed onOct. 10, 2001, the details of which are hereby incorporated byreference. In some embodiments, transaction gateway 102 may includelogic to determine whether to process the money transfer request basedon the outcome of other requests included in the communication. Forinstances, if identity validation service 118 transmits a resultindicating the identification presented may be fraudulent or checkverification service indicates a check may not be valid, the transactiongateway 102 may not route the money transfer request to the moneytransfer system. As another example, a money transfer may not beprocessed if the customer identity is on a prohibited list, such as theOFAC SDN list. Exemplary systems and methods that may be used to check acustomer identity before processing a money transfer request may befound in U.S. application Ser. No. 10/321783, entitled “Methods andSystems for Processing Transaction Requests”, filed Dec. 16, 2002, thedetails of which are hereby incorporated by reference.

It should be appreciated that in alternative embodiments, transactionsystem 100 may include additional or fewer components than illustrated.For instances, transaction system 100 may not include financialinstitution system 110 and/or client computer 114 or alternatively maynot include point-of-sale device 104. As another example, transactiongateway 102 may be communicatively coupled with additional or fewertransaction services 118, 120, 122, 124. Other variations are alsocontemplated.

FIG. 2 illustrates an exemplary embodiment of a transaction gateway 200that may be used to route requests included in a communication to one ormore transaction services. Transaction gateway 200 may include logic 206communicatively coupled with communications interface 202. Acommunicative coupling is a coupling that allows communication betweenthe components. This coupling may be by means of a bus, cable, network,wireless mechanism, program code call (e.g., modular or procedural call)or other mechanism that allows communication between the components.Thus, it should be appreciated that communications interface 202, logic206 or components of logic 206 may reside on the same or differentphysical devices.

Communications interfaces 202 may be used to receive communicationsassociated with customer transactions. Communications interfaces 202 mayalso be used to receive results from transaction services. By way ofexample, communications interface 202 may include an interface to a widearea network (WAN), such as the Internet or proprietary networks.Alternative or additional types of interfaces may also be included ascomponents of communications interface 202.

Logic 206 may be one or more software programs, one or more componentsof a software program (e.g., function or program object), firmware, orother type of machine-executable instructions. In one embodiment, logic206 may include a web service accessed by point-of-sale devices,financial institution systems, or other types of clients. Logic 206 maybe used to route requests included in a transaction communication to theappropriate transaction service and to transmit a response indicatingthe results of the transaction service processing. Thus, logic 206 maybe configured to determine the types of requests included in acommunication and to route the request accordingly. For example, if thecommunication includes an identity verification request, logic 206 maybe configured to transmit the identity verification request to anidentity verification service. As previously described, in someinstances, logic 206 may transmit transaction service requestssimultaneously, while in other instances, logic 206 may ordertransaction service requests, may include the results of a transactionrequest (e.g., identity values obtained from encoded data) in a requestsubmitted to a second service, and/or may not transmit one or more ofthe requests included in a communication based on the outcome of aprevious transaction request. Additional details of functionality thatmay be performed by logic 206 will be described in detail below withreference to FIG. 4.

FIG. 3 illustrates one embodiment of a computer system 300 upon whichcomponents of a transaction system (e.g., transaction gateway, identityverification service) may be implemented. The computer system 300 isshown comprising hardware elements that may be electrically coupled viaa bus 355. The hardware elements may include one or more centralprocessing units (CPUs) 305; one or more input devices 310 (e.g., a scandevice, a mouse, a keyboard, etc.); and one or more output devices 315(e.g., a display device, a printer, etc.). The computer system 300 mayalso include one or more storage device 320. By way of example, storagedevice(s) 320 may be disk drives, optical storage devices, solid-statestorage device such as a random access memory (“RAM”) and/or a read-onlymemory (“ROM”), which can be programmable, flash-updateable and/or thelike.

The computer system 300 may additionally include a computer-readablestorage media reader 325; a communications system 330 (e.g., a modem, anetwork card (wireless or wired), an infra-red communication device,etc.); and working memory 340, which may include RAM and ROM devices asdescribed above. In some embodiments, the computer system 300 may alsoinclude a processing acceleration unit 335, which can include a DSP, aspecial-purpose processor and/or the like.

The computer-readable storage media reader 325 can further be connectedto a computer-readable storage medium, together (and, optionally, incombination with storage device(s) 320) comprehensively representingremote, local, fixed, and/or removable storage devices plus storagemedia for temporarily and/or more permanently containingcomputer-readable information. The communications system 330 may permitdata to be exchanged with a network and/or any other computer or othertype of device, such as a POS device.

The computer system 300 may also comprise software elements, shown asbeing currently located within a working memory 340, including anoperating system 345 and/or other code 350, such as an applicationprogram. The application programs may implement a framework, componentsof a framework, and/or the methods of the invention. It should beappreciated that alternate embodiments of a computer system 300 may havenumerous variations from that described above. For example, customizedhardware might also be used and/or particular elements might beimplemented in hardware, software (including portable software, such asapplets), or both. Further, connection to other computing devices suchas network input/output devices may be employed.

FIG. 4 is a flow diagram illustrating an exemplary method that may beused to process a customer transaction. A point-of-sale device,financial institution system, or other client computer may transmit 402transaction details for a customer transaction to a transaction gateway.The details may include information, such as the transaction amount andpayment information. The communication may also include one or morerequests for transaction services needed to process the transaction.

The communication is received 404 at the transaction gateway. In oneembodiment, the transaction gateway may include a web service and thecommunication may be a Simple Object Access Protocol (SOAP) message orExtended Markup Language (XML) message. In embodiments in which thecommunication is a SOAP message, the header may include a requesteridentity, and a request segment count indicating the number of requestsincluded in the message. Each request may be included in a segment whichidentifies the type of request and includes one or more fields relatedto the request. For example, an identity verification request mayinclude the requester identity and the encoded data read from theidentification. Other communication formats may also be used.

The transaction gateway may then determine 406 the requests associatedwith the communication. One of the requests is routed 408 to theassociated transaction service. By way of example, an identityverification request may be routed to an identity verification service.If there are more requests 410, those are also routed 408 to theassociated transaction service. As previously described, transactiongateway may route some of the requests simultaneously, while otherrequests may depend on the results of a previously routed 408 request.Thus, an identity validation request may not be routed 408 untilidentity values have been obtained from encoded data by an identityverification service. Additionally, in some instances, some requests maynot be routed 408, if a previously result indicates the transactionprocessing should not continue. Thus, for example, if an identityverification service is unable to obtain identity values from encodeddata, a request to perform identity validation may not be routed 408. Asanother example, if there is an indication an identification may befraudulent, a check verification request may not be routed. Other logicmay also be performed by a transaction gateway to determine when and howto route requests for transaction services included in a receivedcommunication.

In some aspects, transaction gateway may receive 412 results from thetransaction services to which requests were routed. The results may eachindicate a result of the respective transaction service processing. Aspreviously described, transaction gateway may use these results inrouting other transaction service requests. Alternatively, results maybe transmitted directly to a requester associated with the communicationby one or more of the respective transaction services and/or thetransaction services may send results to other transaction services.

The transaction gateway may combine 414 the results received into aresponse communication to be transmitted back to the requesterassociated with the received 404 communication. For example, transactiongateway may create a SOAP message with a header indicating the number ofresults, and segments for each result. The result communication may thenbe transmitted 416 to the requester. Alternatively, transaction gatewaymay transmit each result separately or in different combinations.

FIG. 5 is a flow diagram of an exemplary identity verification processthat may be used by an identity verification service. The identityverification process may begin by receiving 502 an identity verificationrequest. The identity verification request includes encoded data readfrom an identification. By way of example, the encoded data may bemagnetic stripe data, two-dimensional bar code data, smart card data, orother type of data. The identification may be a state issuedidentification, a driver's license, a passport, a militaryidentification, or other type of identification.

The identity verification request received 502 may also include arequester identification. The requester identification may beauthenticated 504 by the identity verification service. If theauthentication is not successful, a bad authentication response may betransmitted 510 and processing may be terminated. This may preventunauthorized use of the identity verification service. In otherembodiments, the requester may not be authenticated or may beauthenticated by another component of a transaction system, such astransaction gateway.

If 506 the requester is successfully authenticated, the identityverification service may attempt to parse 508 the encoded data to obtainone or more identification values from the encoded data. The parsing 508may include a determination of the type of identification, the type ofencoded data, and/or the issuing authority. Appropriate algorithms maybe used depending upon this information. If 512 to parse 508 the encodeddata is not successful, a result message may be transmitted by theidentity verification service indicating the error status (e.g., encodeddata has invalid format or is otherwise problematic).

If the parse is successful, one or more identity values are obtainedfrom the encoded data. The identity values obtained may vary dependingupon the type of identification and issuing authority. By way ofexample, the identification values may include one or more of first/lastname, identification number, address, birth date, gender, hair color,height, eye color, weight, restrictions, or other information includedin the encoded data obtained from the identification.

The identity values obtained 508 may be analyzed 514 to determine one ormore verification statuses for the identification. For example, theanalysis may indicate the identification is expired, there are alcoholor tobacco restrictions because of age, or other information. Theanalysis 508 may also indicate that one or more criteria are satisfiedindicating the identification may be fraudulent. For example, one ormore of the identity values obtained may be compared to a data store ofknown or suspicious identifications. As another example, one or moreidentity values may be missing that should have been included. In someaspects, the criteria may include analyzing the number of times anidentity has been presented in a predefined time period to determine ifa predefined threshold has been exceeded. If criteria are satisfied, theidentity verification service may determine 514 the verification statusshould indicate the identity may be fraudulent. The status(es) mayalternatively or additionally include other outcomes of the identityverification process.

Identity verification service may then transmit 518 a resultcommunication to either a transaction gateway, the identity verificationrequester, or another transaction service. The result may include theobtained identity values. The result may also include one or morestatuses, such as those previously described, indicating the outcome ofthe identity verification. The identity values may ultimately becompared by the requester to the physical identification to determine ifthe values match. Alternatively, this information may have also beentransmitted to the transaction gateway for a transaction service (e.g.,identity verification service or identity validation service) to performthe analysis on whether the values match.

In the foregoing description, for the purposes of illustration, methodswere described in a particular order. It should be appreciated that inalternate embodiments, the methods may be performed in a different orderthan that described. Additionally, the methods may contain additional orfewer steps than described above. It should also be appreciated that themethods described above may be performed by hardware components or maybe embodied in sequences of machine-executable instructions, which maybe used to cause a machine, such as a general-purpose or special-purposeprocessor or logic circuits programmed with the instructions, to performthe methods. These machine-executable instructions may be stored on oneor more machine readable mediums, such as CD-ROMs or other type ofoptical disks, floppy diskettes, ROMs, RAMs, EPROMs, EEPROMs, magneticor optical cards, flash memory, or other types of machine-readablemediums suitable for storing electronic instructions. Alternatively, themethods may be performed by a combination of hardware and software.

While illustrative and presently preferred embodiments of the inventionhave been described in detail herein, it is to be understood that theinventive concepts may be otherwise variously embodied and employed, andthat the appended claims are intended to be construed to include suchvariations, except as limited by the prior art.

1. A method comprising: receiving, at a transaction gateway, acommunication associated with a transaction initiated by a customer, thecommunication including one or more requests, each of the requestsassociated with a transaction service; determining, at the transactiongateway, the communication includes an identity verification request toverify encoded data obtained from an identification presented by thecustomer; routing the identity verification request to an identityverification service; receiving, at the transaction gateway, a resultfrom the identity verification service, the result including one or moreidentification values obtained from the encoded data; and transmittingthe result to a requester associated with the communication.
 2. Themethod of claim 1, wherein receiving the result comprises receiving astatus indicating an outcome of the identity verification.
 3. The methodof claim 2, wherein the status indicates the identification is expired.4. The method of claim 2, wherein the status indicates theidentification may be falsified.
 5. The method of claim 2, wherein thestatus indicates a format associated with the encoded data is invalid.6. The method of claim 1, further comprising parsing, at the identityverification service, the encoded data to obtain the one or moreidentification values.
 7. The method of claim 6, further comprising:determining, at the identity verification service, a criteria issatisfied indicating the identification may be fraudulent; andtransmitting, from the identity verification service, the result, theresult indicating the identification may be fraudulent.
 8. The method ofclaim 7, wherein determining the criteria is satisfied comprisesdetermining the identification has been presented a predetermined numberof times within a predetermined time period.
 9. The method of claim 6,wherein parsing the encoded data comprises obtaining an identificationtype from the encoded data.
 10. The method of claim 9, wherein theidentification type is one of a driver's license, a state issuedidentification, a passport, and a military identification.
 11. Themethod of claim 6, wherein parsing the encoded data comprises obtaining,from the encoded data, at least one of a name, a birth date, an address,a gender, a hair color, a height, an eye color, and a weight.
 12. Themethod of claim 6, wherein parsing the encoded data comprisesdetermining a format associated with the encoded data.
 13. The method ofclaim 12, wherein determining the format comprises determining theformat is one of magnetic stripe data, two-dimensional bar code data, orsmart card data.
 14. The method of claim 6, wherein the communication isassociated with a requester, the method further comprising:authenticating the requester before parsing the encoded data.
 15. Themethod of claim 1 further comprising: determining the communicationincludes an identity validation request to assess validity of theidentification; routing the identity validation request to an identityvalidation service; and receiving a validation result indicating anidentification validity status assessed by the identity validationservice.
 16. The method of claim 15, further comprising: at the identityvalidation service, comparing at least one of the identification valuesto a database including suspicious data values; and if theidentification value matches a suspicious data value, setting thevalidation status to an alert status.
 17. The method of claim 15,further comprising: at the identity validation service, matching a firstone of the identification values to a first stored value; retrieving asecond stored value associated with the first stored value, the secondstored value and a second one of the identification values bothassociated with a first identity attribute; and if the secondidentification value does not match the second stored database value,setting the validation status to an alert status.
 18. The method ofclaim 1, further comprising: determining the communication include acheck validation request to analyze a loss potential associated with acheck presented for payment for the transaction; and routing, at thetransaction gateway, the check validation request to a check validationservice.
 19. The method of claim 1, wherein the communication includes aplurality of requests, and wherein transmitting the result comprisestransmitting a result message having a plurality of results, each resultassociated with one of the requests.
 20. The method of claim 1, whereintransmitting the result comprises transmitting the result to apoint-of-sale device.
 21. The method of claim 1, wherein transmittingthe result comprises transmitting the result to a financial institutionsystem.
 22. The method of claim 1, wherein receiving a communicationcomprises receiving one of a Simple Object Access Protocol (SOAP)message or an Extended Markup Language (XML) message.
 23. A methodcomprising: receiving a communication at a transaction gateway, thecommunication associated with a transaction initiated by a customer;determining the communication includes a plurality of transactionservice requests; determining a first one of the transaction servicerequests included in the communication is an identity verificationrequest to verify encoded data obtained from an identification presentedby the customer; transmitting, from the transaction gateway, the firsttransaction service request to an identity verification service;transmitting, from the transaction gateway, a second transaction servicerequest included in the communication to a second transaction service;receiving, at the transaction gateway, a first result from the identityverification service; receiving, at the transaction gateway, a secondresult from the second transaction service; and transmitting, from thetransaction gateway, a response to a requester associated with thecommunication, the response including the first result and the secondresult.
 24. The method of claim 23, further comprising: at the identityverification service, attempting to obtain one or more identificationvalues from the encoded data; if the attempt is unsuccessful,transmitting, from the identity verification service, the first resultto the transaction gateway, the first result including an error status;and if the attempt is successful, transmitting, from the identityverification service, the first result to the transaction gateway, thefirst result message including the one or more identification values.25. The method of claim 24, wherein if the attempt is successful, thetransmitting the first result message further includes transmitting astatus associated with the identity verification.
 26. A systemcomprising: a communications interface, to receive a communicationassociated with a transaction initiated by a customer and to receive anidentity verification result from an identity verification service andone or more additional results; and logic, communicatively coupled withthe communications interface, to determine the communication includes anidentity verification request to verify encoded data obtained from anidentification presented by the customer, to transmit the identityverification request to the identity verification service, to determinethe communication includes one or more additional transaction servicerequests for the transaction, to transmit each of the additionaltransaction service requests to a transaction service associated withthe respective additional transaction service request, and to transmit aresponse to a requester associated with the communication, the responseincluding the identity verification result and the one or moreadditional results.
 27. The system of claim 26, further comprising theidentity verification service to obtain one or more identificationvalues from the encoded data and to transmit the identity verificationresult to the communications interface, the identity verification resultincluding the one or more identification values.
 28. The system of claim27, further comprising: a data store, communicatively coupled with theidentity verification service, to store identity information for aplurality of identifications; and wherein the identity verificationservice is further to compare the one or more identity values obtainedfrom the encoded data to information in the data store to determine ifthe identification may be fraudulent and to include a status indicatorin the identity verification result based at least in part on thecomparison.